Method and system to provide network status information to a device

ABSTRACT

Network status information is provided to a mobile device. The data usage of the mobile device is tracked. A data usage criterion is determined from an account for the mobile device. The account information is stored on at least one server. The data usage is compared with the data usage criterion. Based on the comparison, it is determined whether the data usage meets the data usage criterion. Upon determining that the data usage meets the data usage criterion, a notification message is sent to the mobile device in real time through an information element field within an existing message in a bearer channel of the wireless packet data communication network. The notification message may instruct the mobile device to prevent generation and/or transmission of automatic network access requests while allowing user-initiated network access requests.

BACKGROUND

In recent years, mobile wireless communications have become increasinglypopular. Initial implementations of mobile wireless communications, forexample in the form of cellular telephone networks, supported circuitswitched voice communication services. The carriers developed shortmessage service (SMS) technology to provide text and/or e-mailcommunications via the wireless communication networks. As the publicwireless communication networks have evolved to provide greaterbandwidth and packet based services, the industry has developed avariety of data services, such as web browsing, as well as a variety ofservices using multimedia message service (MMS) technology.

Wireless packet data communication is being provided with everincreasing transmission speed. The packet data communication allowsmobile device users to expand the scope of their use of the mobiledevice, for example, to enjoy multimedia services at a speed comparableto those enjoyed via Internet connected personal computers (PCs).

As the packet data communication has become prevalent, multiple forms ofpayment for networked data communication services have evolved. Multipleaccount options with varying amounts of data usage, call time, qualityof service and bandwidth allowable are available as postpaid and prepaidcommunications services. Prepaid service, in which a customer orsubscriber has fixed availability of usage of a voice or data resource,is becoming as popular as postpaid options.

User accounts supporting data services, alone or in addition to voiceand messaging services, now encompass a vast majority of mobile wirelesscommunications accounts. Prepaid accounts have limits set by the amountsof usage purchased by the users; however, even postpaid accounts mayhave significant usage thresholds, e.g., beyond which the users payhigher rates per usage. Using the example of a prepaid wireless service,the customer may purchase discrete blocks of time or amounts of data formaking voice telephone calls or data communication via a cellulartelephone network, and then purchases a new block or amount of data whenthe previously purchased block or amount is consumed. If additional datais not purchased at this point, service to the device is terminated.Alternatively, a customer may use a postpaid model in which a fixed feeis applied for using a certain amount of a resource within a certaintime cycle (e.g., an amount of data or a number of minutes or messageswithin a month) and which, if used up, may entail a further fee for eachuse of further resources.

Upon connecting to the wireless communications network, the customeraccount is authorized and authenticated, and the network allows a voiceor data call to proceed. For a prepaid account, the network monitors thecustomer's usage time or data and decrements from the customer'saccount. If the account becomes depleted or reaches billing cyclelimits, the system can either prompt the customer to purchase more timeor data, or the system can terminate the call. Another prepaid andpostpaid plan option, however, enables the customer to budget an amountof airtime that will be used during a certain period of time, insuringthat the budget will not be exceeded unless the customer desires moreairtime. For example, a customer may opt to limit wireless communicationairtime for specific phones in the plan (e.g., to prevent exceedingbudgets allocated for their child). A similar plan may be offered fordata communications, e.g. with a set limit on the amount of data.

In another aspect, since many recent packet data communication users areyoung users, parents of the young users may like to keep track of andcontrol usage of packet data communications of their children. As a wayto control usage of data communication by their children, thechildren/parents may want to be notified when the child has reached thesubscription plan limit (which may be prepaid or postpaid).

To address these needs for people to receive notifications of reaching asubscription plan limit or other pre-set usage limit, some wirelesscommunication service providers attempt to provide notifications ofreaching the limit to the customers. The wireless communication serviceproviders, however, do not provide immediate notice of reaching asubscription plan limit. Typically, the amount of use with respect tothe subscription plan limit is checked after the end of each datacommunication session or each billing cycle. Further, thesenotifications typically rely on short message service (SMS)communication, which is not reliable. In this regard, SMS does notprovide for feedback from the receiving mobile device to acknowledgereceipt of the notification transmission. When the mobile device isturned OFF or is out of reach from signaling towers, the mobile devicemay never receive status notifications. Thus, even if a notificationwere sent from a billing server, it may not be successfully received bythe mobile device.

Accordingly, when an account limitation is reached, the mobile devicemay not be aware that it no longer has data/voice access. Thus, themobile device may continue pinging the network to request access,thereby causing significant overhead in terms of network andcommunication resources. Even if the mobile device may receive anaccount notification, there is currently no means from preventingapplications of the mobile device from attempting to connect to thenetwork. As mobile devices are becoming “smarter” by introducing an everincreasing amount of features which make use of the network, the networkresource problem of blocking communication requests with the network isfurther exacerbated.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord withthe present teachings, by way of example only, not by way of limitation.In the figures, like reference numerals refer to the same or similarelements.

FIG. 1 illustrates a wireless packet data communication network forproviding mobile communications for mobile devices as well as a systemproviding a framework for monitoring mobile device network usage andproviding status information to the mobile device.

FIG. 2 illustrates a high level interface block diagram depicting anexemplary system which provides network usage notifications to a mobiledevice.

FIG. 3 illustrates exemplary information content for specific fields ofa protocol configuration option.

FIG. 4 illustrates an exemplary call flow of a new LTE session.

FIG. 5 illustrates an exemplary call flow where a data usage has met apredetermined criterion in the middle of an LTE session.

FIG. 6 illustrates an exemplary call flow where a mobile devicereplenishes its account in order to communicate with the network afterhaving exceeded a usage limit.

FIG. 7 illustrates an exemplary call flow wherein the QoS for a mobiledevice is changed.

FIG. 8 illustrates an exemplary call flow wherein a user of a mobiledevice starts a new data session with the network in an eHRPD.

FIG. 9 illustrates a network or host computer.

FIG. 10 illustrates a computer with user interface elements.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth by way of examples in order to provide a thorough understanding ofthe relevant teachings. However, it should be apparent to those skilledin the art that the present teachings may be practiced without suchdetails. In other instances, well-known methods, procedures, components,and/or circuitry have been described at a relatively high-level, withoutdetail, in order to avoid unnecessarily obscuring aspects of the presentteachings.

The various examples discussed below enable sending notice to a mobiledevice and/or its user of the level of usage versus the amount limit setunder their subscription plan. In one aspect, the mobile device user isnotified upon meeting at least one criterion with respect to data usagevia a wireless communication network. One such criterion is having metor exceeded a data usage threshold. In another example, a criterion is adata usage threshold that is set below the maximum limit to provide theuser some advance warning. An account of the mobile device user haspredetermined criteria such as a maximum subscription plan limit orother criteria defined by a user's plan and data usage balancereflecting an amount of data usage remaining under the plan. If at leastone criterion (e.g., threshold level of data usage) is met, anotification message to the mobile device is sent in real time throughan information element field within an existing message in a bearerchannel of the wireless packet data communication network.

The notification message may also provide instructions to configure themobile device to prevent the device from automatically pinging (e.g.,attempting to connect to) the network for communication, by preventinggeneration and/or transmission of the signal. Such blocking and/ordeactivating automatic network access preserves network andcommunication resources. Further, it reduces mobile device batteryconsumption. User initiated access attempts may be permitted, althoughthey may be redirected so as to prompt the user to increase the usagelimit, e.g., by purchasing more usage under a prepaid account plan.Accordingly, the instructions in the notification message configure themobile device to deactivate or block automatic network access requestsand allow user initiated network access requests.

In one example, when the data usage meets a predetermined criterion, anotification message is sent to the user's mobile device during therespective data session and an option to change subscription plans isprovided. For example, the notification message may be provided on auser interface of the mobile device. For example, the notificationmessage may be provided in the form of a visual or an audible prompt. Inone example, the options are provided as pop-ups on the user interface.

The criterion may be set by the mobile device user, the serviceprovider, or an account holder (who may or may not be the mobile deviceuser—e.g., a parent or relative of the mobile device user). Thecriterion may include multiple thresholds. In this regard, multiplenotification messages each of reaching a different one of the thresholdsmay be sent to the mobile device in real time, at the time when the datausage has reached the threshold. The criterion can also be with respectto different aspects of the user's plan: for example, voice call minutesor data volume downloaded to the mobile device, and the date/time atwhich the network can be accessed. Further, the criterion and therespective notification may be different for a prepaid and a postpaidaccount.

The notification message of the data usage having met a predeterminedcriterion is sent to the mobile device in real time to allow the user toprovide an opportunity to remedy the criterion and again restore fullcommunication ability. For example, the notification message of havingexceeded a threshold level of data usage may allow the user to use anappropriate new subscription plan, which could be prepaid or postpaid,or replenish the data allocation for the billing plan. The user may beable to replenish their account by purchasing more credits (e.g.,recharge the account). A user may update their subscription plan byselecting a different quality of service (QoS) or a different plan fromthe provider. If the status of having met a predetermined criterion ofdata usage is not cured, the mobile device may be prevented fromaccessing the network. Preventing access to the network from the root(at the mobile device level) instead of being rejected by the networkreduces the demand on the network and communication resources.

Reference now is made in detail to the examples illustrated in theaccompanying drawings and discussed below. FIG. 1 illustrates a numberof mobile devices, a mobile communication network coupled to othercommunication networks and several systems/elements associated with orincluded in the mobile network for various functions as may be involvedin monitoring mobile device data usage, determining status of usage withrespect to plan limits and providing real time notification messages.

Hence, FIG. 1 illustrates a mobile communication network 10 as may beoperated by a carrier or service provider to provide a wide range ofmobile communication services and ancillary services or features to itssubscriber customers and associated mobile device users. The elementsgenerally indicated by the reference numeral 10 generally are elementsof the network and are operated by or on behalf of the carrier, althoughthe mobile devices typically are sold to the carrier's customers. Themobile communication network 10 provides communications between mobiledevices as well as communications for the mobile devices with networksand stations 11 outside the mobile communication network 10.

For purposes of later discussion, several mobile devices appear in thedrawing, to represent examples of the mobile devices that may receivevarious services via the mobile communication network 10. Today, mobiledevices typically take the form portable handsets, smart-phones, tabletcomputers or personal digital assistants (PDAs), although they may beimplemented in other form factors, including consumer and businesselectronic devices. The mobile devices 13 a, 13 b, 13 c, and 13 d, forexample, may take the form of a mobile telephone station, enhanced withdisplay and user input capabilities to support certain text and imagecommunications, such as email, picture communication and web browsingapplications.

In another example, as illustrated in FIG. 2, mobile device 13 f is aportable computing device, specifically, comprising a wireless modemcard inserted into a handheld or laptop personal computer (PC) or thelike. Alternatively, the PC may connect to a handset device, similar tothe handset type mobile device 13 a. The mobile device 13 a includes awireless transceiver compatible with the particular type of packet dataservice offered by the system 10. For discussion of one usagenotification message example and the associated exemplary notificationservice, we assume that the mobile devices 13 a, 13 b, 13 c, 13 d, 13 e,and 13 f are all covered under one subscriber account, and that amongthose stations, the mobile device 13 a is the station of the accountholder (AH).

Returning to FIG. 1, the network 10 allows users of the mobile devicesto initiate and receive telephone calls to each other as well as throughthe public switched telephone network (PSTN) and telephone stationsconnected thereto. The network 10 allows SMS type text messaging betweenmobile devices and similar messaging with other devices via theInternet. The network 10 typically offers a variety of other dataservices via the Internet, such as downloads, web browsing, e-mail, etc.

The mobile communication network 10 typically is implemented by a numberof interconnected networks. Hence, the overall network 10 may include anumber of radio access networks (RANs), as well as regional groundnetworks interconnecting a number of Radio Access Networks (RANs) and awide area network (WAN) interconnecting the regional ground networks tocore network elements, such as the Multimedia Messaging Service Centers(MMSCs). A regional portion of the network 10, such as that servingmobile devices 13 a to 13 f will typically include one or more RANs anda regional circuit and/or packet switched network and associatedsignaling network facilities.

Physical elements of a RAN, operated by one of the mobile serviceproviders or carriers, include a number of base stations represented inthe example by the base stations (BSs) 19. Such base stations 19typically comprise a base transceiver system (BTS) which communicatesvia an antennae system at the site of base station and over the airlinkwith one or more of the mobile devices 13 a to 13 f when the mobiledevices are within range. Each base station 19 typically includes a BTScoupled to several antennae mounted on a radio tower within a coveragearea often referred to as a “cell.” The BTS is the part of the radionetwork that sends and receives RF signals to/from the mobile devicesthat the base station currently serves.

The radio access networks also include a traffic network representedgenerally by the cloud at 21, which carries the user communications forthe mobile devices 13 a to 13 f between the respective base stations 19and other elements with or through which the mobile devices 13 a to 13 fcommunicate. Individual elements such as switches and/or routers formingthe traffic network 21 are omitted here form simplicity.

The traffic network portion 21 of the mobile communication network 10connects to a public switched telephone network (PSTN) 23. This allowsthe network 10 to provide voice grade call connections between mobiledevices and regular telephones connected to the PSTN 23. The drawing inFIG. 1 illustrates one such telephone at 25. The PSTN 23 also providesconnections to other types of customer premises equipment, such asfacsimile or ‘FAX’ machines (not shown).

The traffic network portion 21 of the mobile communication network 10connects to a public packet switched data communication network, such asthe network commonly referred to as the “Internet” shown at 29. Packetswitched communications via the traffic network 21 and the Internet 29may support a variety of user services through the network 10, such asmobile device communications of text and multimedia messages, e-mail,web surfing or browsing, programming and media downloading (includingaudio and video), etc. For example, the mobile devices may be able toreceive messages from and send messages to user terminal devices, suchas personal computers, either directly (peer-to-peer) or via variousservers (not separately shown). The drawing shows one such user terminaldevice as a personal computer (PC) 31 or servers 31, by way of example.For purposes of discussing notification messages, some notifications mayentail an e-mail message transmission of the notification to the accountholder's terminal, such as to the PC 31 via the Internet 29.

Of note for purposes of this discussion, many of the network usagenotification messages discussed herein are sent to various mobiledevices using the packet data network (PDN) 21. The Evolved Packet Core(EPC) of network 21 uses the concept of Evolved Packet System (EPS)bearer channels to route IP traffic from a gateway 107 in the network 21to the mobile device (e.g. 13 a to 13 f). A bearer channel is an IPpacket flow with a defined quality of service (QoS) between the PacketData Network (PDN) Gateway (PGW) 107 and the mobile device (e.g., 13 ato 13 f). It is within these packets that notification messages to amobile device (13 a to 13 f) are sent. For example, when a mobile device13 a has met a predetermined account criterion, e.g., has depleted anaccount balance, the network 10 provides a notification message in aninformation element field within an existing message from the network 21to the device (e.g., 13 a to 13 f). In one example, the notificationmessage is embedded in the protocol configuration option (PCO) in themessage to the device through the bearer control plane. For example, thenetwork provides a notification message, options to replenish/change theaccount, and possible instructions to prevent subsequent pinging to thenetwork 21. The PCO is an information element field within the existingmessage from the network 21 to the device (e.g., 13 a to 13 f). Thus,the PCO may be used to provide having met certain criterion-relatedinformation and/or the instructions to the mobile device in connectionwith account network usage and possible further related action, likepreventing further automatic pinging originating from the mobile device.

For example, this notification message may be transmitted in real time.In some cases, the network 10 may also send a notification message tothe mobile device of one or more other users on the account. Hence, inour example, when any mobile device (e.g., 13 b) meets a predeterminedaccount criterion, the network 10 might also provide a notificationmessage in the form of a PCO message sent via the gateway 107, thetraffic network 21, one of the base stations 19 and a signaling channelover the air link to the remaining mobile devices (e.g., 13 a, 13 c, and13 d).

The carrier also operates a number of systems that provide ancillaryfunctions in support of the communications services provided through thenetwork 10, and those elements communicate with other nodes/elements ofthe network 10 via one or more private IP type packet data networks 35(sometimes referred to as an Intranet). The support elements, forexample, include one or more systems of record, such as the system shownat 39. For example such a system 39 may include subscriber accountrecords. A large carrier typically has a number of such systems, and thesystem that stores the account data for a particular subscriber may bereferred to as the “system of record” for that subscriber's account.

Some of the users of the mobile devices will subscribe to voice and/ordata services under one or more post-pay service plans offered by acarrier or service provider. However, the users or subscribers of otherstations will subscribe to voice and/or data services under a plan, inwhich they pay in advance for an amount of communication service usage.In the examples, usage is measured by duration, e.g., length of time ofa voice call, length of time of a data communication session, volume ofthe consumed data, and/or simply packets of data communicated with aguaranteed QoS supporting real-time communications of an appropriatebandwidth.

For example, the online charging system (e.g., OCS 208) provides thenotification message to a mobile device (e.g., 13 a to 13 f) in the formof a PCO in the bearer channel. The notification message is sentsubstantially at the time the data usage meets a predeterminedcriterion. The PCO, in one embodiment, is a type 4 information elementwith a minimum length of 3 octets and a maximum length of 253 octets(see, e.g., 3GPP TS 24.008 V10.3.0). For example, the PCO may includethe following information to a mobile device (e.g., 13 a to 13 f):

0001H (P-CSCF IPv6 Address);

0002H (IM CN Subsystem Signaling Flag);

0003H (DNS Server IPv6 Address);

0004H (Policy Control rejection code);

0005H (Selected Bearer Control Mode);

0006H (Reserved);

0007H (DSMIPv6 Home Agent Address);

0008H (DSMIPv6 Home Network Prefix);

0009H (DSMIPv6 IPv4 Home Agent Address);

000AH (Reserved);

000BH (Reserved);

000CH (P-CSCF IPv4 Address);

000DH (DNS Server IPv4 Address);

000EH (MSISDN);

000FH (IFOM-Support);

0010H (IPv4 Link MTU); and

FF00H to FFFFH reserved for operator specific use.

In one example, where a predetermined criterion is met, the containeridentifier inside the PCO is set to one of the reserved fields FF00H toFFFFH to provide usage information to the mobile device in thenotification message. Further, the container identifier fields FF00H toFFFFH can be used to provide instructions to the mobile device 13 todeactivate, block, or restrict the network pinging by the mobile device13.

FIG. 3 illustrates exemplary information container content for fieldsFF00H to FFFFH that is tailored for each specific mobile device (e.g.,13 a to 13 f). For example, by specifying ACTION=2, the mobile devicemay be denied network access except for IP addresses which allow achange or replenishment of the subscription plan, once an accountcriterion is met. In another example, an ACTION=3, redirects the mobileuser to a site in connection with a specific provider, while denying anyother network access. For a prepaid phone situation, the user of themobile device may be redirected to the site of the prepaid phoneprovider, such that the user can replenish or update their mobile deviceaccount. For example, the user can replenish their account by purchasingmore credits (e.g., recharge the account). As to updating their account,a user may change the QoS or change to a different plan from theprovider. The user of the mobile device can generally accessreplenishment web-sites even when an account criterion is reached (e.g.,in either ACTION=2 or 3).

A method of notifying the mobile device regarding data usage can includethe steps of tracking an amount of data usage being used by the mobiledevice. This tracking may occur at the PGW server 107 communicating withthe mobile device through the mobile network 21. It can then bedetermined, from the user account for the mobile device a first datausage limit and a first data usage time frame. For example, the timeframe may be the time of day/week (e.g., 6 a.m. to 6 p.m.; Monday toFriday or weekend). The user account information typically is stored onthe server, such as OCS server 208. The OCS server 208 can thendetermine whether a criterion is met by comparing the amount of datausage to the first data usage limit and comparing a present time to thefirst data usage time frame. In this regard, there may be “time of day”restrictions. From this comparison, a data usage amount for the firstdata usage time frame is determined. Consequently, it can be determinedwhether the data usage amount exceeds the first data usage limit. Upondetermining that the data usage amount meets a criterion (e.g., is equalto or exceeds the first data usage limit in the first data usage timeframe), then the system sends a notification message to the respectivemobile device. Additionally, one or more data usage limits may becompared to other usage limits. For example, a second criterion may berelated to time of day/week; volume; communication with specifictelephone numbers or sites; and the like. For example, there may feweror even no restrictions at nights or weekends. Further, certain phonenumbers or web sites may be blocked by the account holder. If the seconddata usage limit meets a respective predetermined usage criterion, theOCS server 208 provides a notification message to the mobile device. Forexample, the account holder may specify on the customer account webserver 43 that the first notification message should be sent to therespective mobile device that has met the first account criterion (e.g.,data usage limit) while the second notification message may be sent toall mobile devices on the account. In another example, all notificationmessages are sent to the account holder and the respective mobile devicethat has met an account criterion.

In one example, the notification message provided by the OCS server 208in connection with meeting a predetermined account criterion (e.g.,exceeding a usage data limit) includes a suggestion to change orreplenish the subscription plan. This type of suggestion can be appliedto either or both prepaid or postpaid subscription plans. Thenotification message in connection with meeting a predetermined accountcriterion may be different depending on whether the subscription plan isprepaid or postpaid. Thus, the notification message can be specializedto the type of subscription plan. The mobile device may include one ormore clients (e.g., application programs) that run on the mobile deviceand that are configured to receive input and/or instructions from theOCS server 208 through the network 21. In one example, a client triggersa pop-up message on the mobile device 13 a offering differentsubscription or replenishment options. For example, the user may benotified that their account has run out of money, has reached a datalimit, or is under a data restriction. An option may be provided toallow the user of the mobile device (e.g., 13 a) to suspend theirservice, or the service of individual mobile devices under the user'saccount (e.g., 13 a to 13 f), until the next billing cycle rolls aroundso the account does not enter into overages. Further, a clientdeactivates the mobile device communication capability with the network.The deactivation may be performed by the same client that triggers thepop-up message or a separate client. The client receives deactivationinstructions from the notification message. In one example, allautomatic (not manually/user-triggered) communication requests fromapplications on the mobile device are deactivated by the client blockingthe IP stack with respect to internet traffic. Thus, automatic pingingof the network is prevented unless in response to a request tocommunicate with the network that is specifically initiated by themobile device user. Put differently, a request to communicate with thenetwork that is initiated by the mobile device user is treateddifferently from automatic pinging by applications of the mobile device.In this regard, a request to communicate with the network may result inthe user being redirected on their mobile device to a web-site that canprovide replenishment or a modification of their account (i.e.,subscription plan). Accordingly, a repeated pinging of the network by amobile device that has met a predetermined account criterion isprevented, thereby saving network resources.

In a further example of a method of sending a notification message to amobile device 13 a in a communication network 21 regarding meeting apredetermined account criterion, an OCS 208 detects real-time mobiledevice 13 a data usage and a present time. The OCS 208 accesses theaccount data for the mobile device 13 a and determines a usage datalimit. In one example, it also determines an account cycle. The accountdata is stored in the OCS 208 or in a separate server. A calculation isperformed, based on the real-time mobile device data usage, the usagedata limit, the present time, and the account cycle, to determine acurrent usage amount and a time remaining in the cycle. The data usageis calculated at the present time to determine whether the usage datalimit has been exceeded. If there is an event corresponding to a triggerdefined by allocated usage, the OCS 208 detects that event and generatesa notification message for transmission via the network 35. For example,upon determining in real time that the current data usage limit isexceeded, a notification message is provided to the mobile device 13 awith a suggestion to either replenish the account or to change to adifferent subscription plan. Further, the mobile device is preventedfrom pinging the network for communication unless it is initiated by themobile device 13 a user.

In one example, network 10 also includes a customer communicationssystem 41, which is coupled for communication via the private network35. The customer communications system 41 receives the notificationrequest message from the OCS 208; and in response, generates and sendsone or more notification messages. For example, the customercommunications system 41 may generate and send the notification messagein a PCO in the bearer channel to the mobile station 13 a designated asthat of the account holder and/or to the mobile other stations 13 b to13 f that are on the account.

In one example, the carrier also offers its subscribers on-line accessto a variety of functions related to the subscribers' accounts, such asreview of billing statements and usage data, on-line payment,subscription changes, password control or the like. For that purpose,the carrier in our example operates a customer account web server 43,providing a subscriber interface via the Internet. Hence, a user'sterminal, such as PC 31, may be used to access on-line information abouta subscriber's account, which the mobile carrier makes available via thecarrier's web site accessible through the Internet 29.

In the example of FIG. 1, when the OCS 208 detects account usage thatmeets a predetermined account criterion (e.g., exceeds a presetthreshold level), it generates and sends a notification request messageto the customer communication system 41. In one example, the OCS 208itself sends one or more notification messages. However, by using acustomer communication system 41, the workload on the data aggregator208 is reduced and application of more sophisticated logic or ‘businessrules’ to the notification messages regarding various types of usage andwhat is preferred by the various subscribers is facilitated.Accordingly, in the mobile communication network 10, the data aggregator208 generates a request message for a notification message to be sent tothe mobile station that a subscriber usage limit has been exceeded, andthe OCS 208 sends that notification request message through thecarrier's private network 35 to the customer communication system 41.The notification request from the OCS 208 to the customer communicationsystem 41 is different from the notification message from the customercommunication system 41 to the mobile device in that it does not includethe additional logic or business rules that the customer communicationsystem 41 provides.

The customer communication system 41 may be implemented on a singlehardware platform. However, to provide effective notification servicesfor a large number of customers and a large volume of trigger events,the customer communication system 41 for the associated example of usagenotification service and other enterprise applications requiringnotification may utilize a distributed system architecture.

FIG. 2 illustrates a high level interface block diagram depicting anexemplary system which provides network usage notification messages to amobile device. For example, the System Architecture Evolution (SAE) 20is the core network architecture of Third Generation PartnershipProject's (3GPP's) Long Term Evaluation (LTE) wireless communicationstandard. The SAE 20 has a flat, all-IP architecture with separation ofcontrol plane and user plane traffic. The SAE 20 system includes eNodeB(eNB) 19, Mobility Management Entity (MME) 202, Home Subscriber Server(HSS) 204, and the Policy Control and Charging Rules Function (PCRF)206, which are part of the network 35 of FIG. 2. As will be described ina later section, eNB 19 is an enhanced base station that acts as aninterface between the mobile device and the mobile network. MME 202 is acontrol-node for the communication access network. For example, it isused for idle mode mobile device tracking and paging procedure includingretransmissions. It also provides bearer channel activation/deactivationprocess and selection of the serving gateway (SGW) 212 for the mobiledevice (e.g., 13 e). MME 202 also provides authentication of the user byinteracting with the Home Subscriber Server (HSS) 204. The MME 202 alsoterminates the S6 a interface towards the HSS 204 for roaming mobiledevices 13 e and 13 f.

The Home Subscriber Server (HSS) 204 is a central database that containsuser-related and subscription-related information. The HSS 204 providesfeatures such as mobility management, call and session establishmentsupport, user authentication and access authorization. For example, theHSS stores the Mobile Station International Subscriber Directory Number(MSISDN), the SIM-card identification information, and the like.

The Packet Data Network (PDN) Gateway (PGW) 107 provides connectivityfrom the mobile devices 13 e and 13 f to external packet data networks.It is a point of exit and entry of traffic for the mobile devices 13 eand 13 f of FIG. 2. The PGW server 107 monitors how much data is used bya mobile device (e.g., 13 e, and 130 at any given time.

The Policy Control and Charging Rules Function (PCRF) 206 provides forpolicy control decision-making, as well as for controlling theflow-based charging functionalities in the Policy Control EnforcementFunction (PCEF), which resides in the PGW 107. The PCRF 206 provides theQoS authorization that decides how certain data flow is treated in thePCEF and ensures that this is in accordance with the user's subscriptionprofile.

The Online Charging System (OCS) server 208 provides real time creditcontrol and charging for communication services. For example, itprovides an account balance management function, credit controlinformation, and allows a communications service provider to chargetheir customers, in real time, based on service usage. The OCS server208, instructs the PGW server 107 how much data the user is allowed touse (e.g., data quota). The OCS determines whether a predeterminedaccount criterion has been met.

The Serving Gateway (SGW) 212 routes and forwards data packets to themobile devices 13 e and 13 f through the MME 202. For example, a datapacket can include a notification message that an account threshold isexceeded. The SGW 212 manages and stores mobile device parameters of theIP bearer channel service, including network internal routinginformation.

With the foregoing overview of the system, it may be helpful now toconsider a high-level discussion of an example of a notification messageof a mobile device and control of the network pinging thereof FIG. 4illustrates an exemplary call flow of a 3GPP Long Term Evolution (LTE)session wherein a mobile device attempts to communicate with the network(i.e., a new call session).

In step 1, the mobile device (UE) 13 initiates a new PDN connection bysending a PDN Connectivity Request to the MME 202.

In step 2, the MME 202 sends a Create Session Request to the SGW 212 tocreate a data session.

In step A1, the SGW 212 forwards the Create Session Request to the HSS204 server to create the data session.

In step A2.1, the PGW 107 sends an Authentication Authorization Request(AAR) to 3GPP Authentication, Authorization, and Accounting (AAA) server204 to authorize the Internet APN for the subscriber. For example,server 204 provides authentication of the mobile device and/or user anddetermines if the mobile device and/or user is authorized to use anetwork service. Further, it accumulates accounting records that couldbe used for billing purposes. Although server 204 may physically be asingle server, it can perform the functions of the AAA, SubscriptionProfile Repository (SPR), and HSS.

In step A2.2, the 3GPP AAA retrieves the profile for the mobile devicefrom the HSS 204 server.

In step A2.3, the 3GPP AAA sends the retrieved subscriber profile fromthe HSS 204 server for the particular mobile device to the PGW 107server.

In step A3, the PGW 107 server sends a Credit Control Request (CCR) tothe PCRF 206 server to request policy information in connection with themobile device.

If the PCRF 206 does not have the subscriber's subscription relatedinformation, in step S1, the PCRF 206 server sends a User Data Request(UDR) to the Subscription Profile Repository (SPR). In one example, theSPR is part of the HSS 204 server.

In step A4, the PCRF 206 sends back the policy and the QoS informationto the PGW 107.

In step A5, the PGW 107 sends an Authentication Authorization Request(AAR) to the 3GPP AAA and receives an Authentication, Authorization, andAccounting (AAA) in response.

In step X1, the PGW 107 server sends a Credit Control Request to the OCSserver 208 to obtain data quota therefrom. The OCS server 208 determineswhether a predetermined account criterion has been met.

Perhaps it may be now be helpful to discuss the different roles the PGW107 server and the OCS server 208 in determining whether an accountcriterion has been met. As discussed before, the PGW server 107 is partof the data path and monitors how much data is used at any given time.As to the OCS server 208, it instructs the PGW server 107 how much datathe user is allowed to use. When the data quota is depleted, the PGWreports this depletion to the OCS and inquires whether additional quotais available. Thus, the PGW makes an initial determination that the dataquota is depleted. The OCS makes the actual determination, as discussedbelow.

In step X2, the OCS server 208 provides a response to the PGW 107server. For example, the response includes a Credit Control Responsewith a cause code, a Final Unit Indication (FUI), and a Filter-ID toindicate to the PGW 107 that the subscriber has no quota available.Thus, although the PGW makes the initial determination that apredetermined account criterion is met, it is in this step (in the OCSserver 208) where the determination is made whether a predeterminedaccount criterion is met. In this regard, the Filter-ID, and may providethe PGW the customer status with respect to whether it is a prepaid orpostpaid type account, the usage criteria, and the related balanceinformation.

In step X3, the PGW 107 server sends a credit notification to the PCRF206 with FUI and Filter-ID.

In step X4, the PCRF 206 server provides special policy rules to the PGW107 server. For example, different data rates may be applied and/or themobile device could be redirected to account replenishment sites.

In step A6, the PGW 107 server processes the special policy rules itobtained from the PCRF 206 server. The PGW 107 server indicates to theSGW 212 server when the customer has no quota, returning a CreateSession Response with the new PCO information with the relevant actioncode, as provided in FIG. 3.

In step 3, the SGW 212 server provides a Create Session Response to theMME 202 server with the PCO information.

In step 4, the MME 202 server sends Evolved Packet System Radio AccessBearer (E RAB) request (e.g., Activate Default EPS Bearer ContextRequest) to the eNodeB eNB (i.e., base station 19 from FIG. 1) whichincludes the PCO information. The eNB is an enhanced base station thatacts as an interface between the mobile device and the mobile network.Node B is a term used in LTE to describe the components equivalent tothe base transceiver system (BTS) in some mobile networks.Traditionally, a BTS is controlled by a Radio Network Controller (RNC).However, in later iterations of LTE, the NodeBs are enhanced withcontrol functionality to effectively replace or eliminate the separateRNC. At least in some examples, NodeB is the equivalent of base stationor BTS; and the term eNodeB or eNB stands for “evolved NodeB.”

In step 5, the eNB sends a Radio Resource Control (RRC) connectionre-configuration request to the mobile device (UE). The mobile deviceparses the PCO information to retrieve subscriber status and followsinstructions therein. For example, when the mobile device (UE) receivesthe PCO information sent in the notification message from the network,the mobile device parses the information and interprets the instructionstherein. Based on the action code obtained and the mobile device client,the mobile device can now block the IP protocol layer level and/orinstruct the client to stop pinging the network. Further, the client onthe mobile device may also disable the capability of applications toengage in any network traffic. Not only does the blocking preservenetwork resources, the battery consumption of the mobile device isreduced as well.

In step 6, the mobile device (UE) returns the RRC ConnectionConfiguration Complete to the eNB, thereby acknowledging that theinstructions have been successfully received.

In step 7, a regular call session is established. Alternatively, if apredetermined account criterion is met (e.g., an account threshold isexceeded), a regular call session is prevented. Accordingly, FIG. 4describes a scenario in which a mobile device attempts to create a newnetwork session and the determination of whether an account criterionhas been met.

An account criterion can of course also be met in mid session. In thisregard, FIG. 5 illustrates an exemplary call flow of a 3GPP Long TermEvolution (LTE) session where a mobile device continues to communicatewith the network after having exceeded a usage limit. In step B1, thePacket Data Network (PDN) Gateway (PGW 107) server sends a CreditControl Request (CCR) to the OCS server 208 to request the data quota.As discussed before, the PGW 107 tracks data usage of the mobile device.The OCS server 208 has account information, including predeterminedaccount criteria. At the beginning of the mobile device data session,the PGW 107 obtains the account criteria. Once the PGW 107 determinesthat a predetermined account criterion is met, the PGW 107 requests theaccount criteria again from the OCS server 208 to confirm that theaccount criterion has indeed been met. Thus, although the PGW makes theinitial determination whether an account criterion is met, the OCS makesthe actual determination that an account criterion has been met.

In step B2, the OCS responds to the PGW 107 server by providing a CCRwith a cause code, Final Unit Indication (FUI) and Filter ID. In thisexample, the OCS indicates to the PGW 107 that the subscriber has met apredetermined criterion (e.g., has no quota available).

In step C1, the PGW 107 server provides a credit notification to thePCRF 206 with the FUI and Filter ID.

In step C2, after receiving the credit notification, the PCRF 206responds to the PGW 107 by providing the special policy rules inconnection with the account.

In step 1 of FIG. 5, the HTTP traffic continues. The session is allowedto continue because the mobile device (UE) 13 has not been notified yet.Accordingly, the mobile device has not been given an opportunity to curehaving met at least one predetermined account criterion.

In step 2, the PGW 107 server processes the special policy rules. Forexample, the policy rules indicate that the mobile device met apredetermined account criterion (e.g., has no more quota). A CreateSession Response is provided with new PCO information. The PCO includesa notification message that the mobile device has met a predeterminedaccount criterion (e.g., exceeded at least one threshold limit of datausage). In one example, the PCO includes instructions to deactivate thenetwork pinging by the mobile device if the account is not replenishedor recharged. Accordingly, clients on the mobile device are preventedfrom automatically seeking network access. In one example, onlyuser-initiated interactions with the network are allowed to reach thenetwork.

In step 3, the SGW 212 server provides the Create Session Response tothe MME 202. The response from the SGW 212 server to the MME 202includes the PCO information.

In step 4, the MME 202 server sends an Evolved Packet System RadioAccess Bearer (E RAB) setup request (e.g., to modify the EPS Bearercontext request) to the eNodeB (eNB) that includes the PCO information.

In step 5, the eNB sends a Radio Resource Control (RRC) connectionre-configuration request to the mobile device (UE). Thus, the mobiledevice receives the notification message through a PCO in a bearerchannel of the wireless packet data. The mobile device parses the PCOinformation to retrieve subscriber status and follows instructionstherein. For example, the PCO may include instructions to deactivate anynetwork pinging from the mobile device. Further, the PCO may includeinstructions to only allow user-initiated interactions with the network.The mobile device may be provided a link (e.g., through pop-up) to asite to replenish/change the subscription plan.

In step 6, the mobile device (UE) returns the RRC ConnectionConfiguration Complete to the eNB.

In step 7, the eNB acknowledges the bearer channel modification bysending a signal to the MME 202 with an E-RAB Modify Response.

In step 8, the mobile device (UE) Non Access Stratum (NAS) layer buildsa NAS level Modify EPS Bearer Context Accept message and sends it insidethe up-link (UL) Information Transfer (i.e., Modify EPS Bearer ContextAccept) message to the eNB. The NAS protocols form the highest stratumof the control plane between the mobile device and the MME 202. NASprotocols support the mobility of the mobile device and the sessionmanagement procedures to establish and maintain IP connectivity betweenthe mobile device and the PDN and network gateways. In one example, theNAS also enforces roaming restrictions of the mobile device.

In step 9, the eNB sends an UL NAS Transfer (e.g., Modify EPS BearerContext Accept) message to the MME 202 server.

In step 10, the MME 202 server sends the Update Bearer Response to theSGW 212 server.

Next, in step 11, the SGW 212 sends the Update Bearer Response to thePGW 107 server.

In step 12, the session continues as normal, providing communicationbetween the mobile device and the network (i.e., network 21 of FIG. 1).For example, the user of the mobile device is able to continue to browsethe internet, watch movies, place calls, etc.

A subscriber of a subscription plan can recharge their mobile devicesubscription plan in mid session. In this regard, FIG. 6 illustrates anexemplary call flow where a mobile device recharges its account in orderto communicate with the network after having met an account criterion(e.g., usage limit). In step A1, the Online Charging System (OCS) serversends a Re-Authorization Request (RAR) to the Packet Data NetworkGateway server (PGW 107).

In Step A2, the PGW 107 returns a Re-Authorization answer (RAA) to theOCS, thereby acknowledging the request.

In step B1, the PGW 107 sends a Credit Control Request Update (CCRU) tothe OCS to determine the quota.

In step B2, the OCS responds to the PGW 107 by providing a quotaassociated with the Rating Group (RG) (i.e., specific service inconnection with the account).

In step C1, the PGW 107 sends an event trigger to the PCRF 206 to notifythat the recharge has occurred.

In step C2, the PCRF 206 responds by providing the policy rules to thePGW 107. For example, this response indicates that the account holderhas sufficient (or insufficient) quota.

In step 2, the PGW 107 server processes the special policy rules, whichindicates that the account holder has sufficient quota (e.g., has notmet a predetermined account criterion). A Create Session Response isprovided with new PCO information. The PCO includes a notificationmessage that the mobile device has not exceeded any threshold limits ofdata usage (i.e., has not met a predetermined account criterion).

In step 3, the SGW 212 server returns the Update Bearer Request to theMME 202 server. The response from the SGW 212 server to the MME 202server includes the PCO information.

In step 4, the MME 202 server sends an Evolved Packet System RadioAccess Bearer (E RAB) modify request (e.g., to modify the EPS Bearercontext request) to the eNodeB (eNB) which includes the PCO information.

In step 5, the eNB sends a Radio Resource Control (RRC) connectionre-configuration request to the mobile device (UE). The mobile deviceparses the PCO information to retrieve subscriber status and followsinstructions therein.

In step 6, the mobile device (UE) returns the RRC ConnectionConfiguration Complete to the eNB.

In step 7, the eNB acknowledges the bearer channel modification bysending a signal to the MME 202 with an E-RAB Modify Response.

In step 8, the mobile device (UE) Non Access Stratum (NAS) layer buildsa NAS level Modify EPS Bearer Context Accept message and sends it insidethe UL Information Transfer (i.e., Modify EPS Bearer Context Accept)message to the eNB. The NAS protocols form the highest stratum of thecontrol plane between the mobile device and the MME 202. NAS protocolssupport the mobility of the mobile device and the session managementprocedures to establish and maintain IP connectivity between the mobiledevice and the PDN and network gateways. In one example, the NAS alsoenforces roaming restrictions of the mobile device (UE) 13.

In step 9, the eNB sends an UL NAS Transfer (e.g., Modify EPS BearerContext Accept) message to the MME 202 server.

In step 10, the MME 202 server sends the Update Bearer Response to theSGW 212 server.

Next, in step 11, the SGW 212 sends the Update Bearer Response to thePGW 107 server.

In step 12, the session continues as normal, providing communicationbetween the mobile device and the network.

The quality of service (QoS) can be affected if a subscriber has met apredetermined account criterion. As discussed above, a bearer channel isan IP packet flow with a defined quality of service (QoS) between thePacket Data Network (PDN) Gateway (PGW 107) and the mobile device. Thenetwork-initiated QoS control paradigm specified in EPS is a set ofsignaling procedures for managing bearer channels and controlling theirQoS assigned by the network. The EPS QoS concept is class-based, whereeach bearer channel is assigned one and only one QoS class identifier(QCI) by the network. The QCI is a scalar that is used within the accessnetwork as a reference to node-specific parameters that control packetforwarding treatment. This class-based approach, together with thenetwork-initiated QoS control paradigm, gives network operators fullcontrol over the QoS provided for its offered services for each of itssubscriber groups. In one example, when a subscription plan limit is metor exceeded, the QoS is lowered. Alternatively, the user of the mobiledevice may be prompted to change their subscription plan to a higherQoS.

FIG. 7 illustrates an exemplary call flow where the QoS for a mobiledevice is changed. FIG. 7 is substantially similar to the call flowdescribed in the context of the discussion of FIG. 5 above and thecorresponding steps are therefore not repeated here for brevity. Onedifference between FIG. 5 and FIG. 7 is that in FIG. 7 the informationpassed from the OCS (i.e., the filter ID and FUI) is different in termsof the special policy rules. For example, in step C2 of FIG. 7, adifferent QoS policy can be applied from the PCRF to the PGW.

The foregoing teachings are also compatible with Evolved High RatePacket Data (eHRPD), which is a method that allows the mobile operatorto upgrade their existing HRPD packet core network using elements of theSAE/EPC architecture. For example, eHRPD is an evolutionary path to LTEwhich provides seamless service mobility between the eHRPD and LTEnetworks. For example, eHRPD has the ability to provide seamless servicemobility between High Rate Packet Data (HRPD) and LTE access networkswith a single mobility management protocol. The operator can leveragethe benefit of optimized handover (e.g., no dropped sessions and reducedhandover latency) between LTE and eHRPD.

FIG. 8 illustrates an exemplary call flow wherein a user of a mobiledevice starts a new data session with the network in an eHRPD. In FIG.8, a High Rate Packet Data Serving Gateway (HSGW) replaces the MME 202of FIGS. 1 to 7.

In step 1, the user of the mobile device (UE) 13 initiates a Point toPoint Protocol, Vendor-Specific Network Control Protocol Configuration(PPP-VSNCP-Config) request to the High Rate Packet Data Serving Gateway(HSGW) to start a new data session between the mobile device and thenetwork.

In step 2, the HSGW sends a Credit Control Request Initial (CCR-I) tothe PCRF 206 server.

In step 3, the PCRF 206 returns a Credit Control Answer Initial to theHSGW server.

In step 4, the HSGW sends a Proxy Mobile IPv6 (PMIPv6 or PMIP) BindingUpdate to the PGW 107 server. A PMIP is a standardized network protocolfor building a common access technology independent of mobile corenetworks accommodating various access technologies, including 3GPP,3GPP2, and WLAN based access architectures.

In step 5, the PGW 107 sends an Authentication Authorization Request(AAR) to Authentication, Authorization, and Accounting (AAA) toauthorize the Internet APN for the subscriber.

In step 6, the 3GPP AAA sends the retrieved subscriber profile from theHSS 204 server for the particular mobile device to the PGW 107 server.

In step 7, the PGW 107 server sends a Credit Control Request Initial(CCR-I) request to the PCRF 206 server to request policy information inconnection with the mobile device.

In step 8, the PCRF 206 sends back a Credit Control Answer Initial(CCA-I) and the policy to the PGW 107 server.

In step X1, the PGW 107 server sends a Credit Control Request to the OCSserver to obtain data quota therefrom.

In step X2, the OCS server provides a response to the PGW 107 server.For example, the response includes a Credit Control Response with acause code, a Final Unit Indication (FUI), and a Filter-ID to indicateto the PGW 107 that the subscriber has no quota available.

In step A1, the PGW 107 server sends an Authentication AuthorizationRequest (AAR) to the 3GPP Authentication, Authorization, and Accounting(AAA) to authorize the Internet APN for the subscriber.

In step A2, the AAA responds with an AAA response to the PGW 107 server.At the same time (in step X3), the PGW 107 server sends a creditnotification (CCRu) to the PCRF 206 server to indicate that apredetermined account criterion is met (e.g., data quota has been usedup). In one example, the PCRF 206 server may implement a differentpolicy by downgrading the QoS, redirection, or restriction.

In step X4, the PCRF 206 server provides special policy rules to the PGW107 server, indicating that the user of the mobile device has run out ofquota.

In step 9, the PGW 107 server processes the special policy rules. Thesepolicy rules indicate that an account criterion is met (e.g., the mobiledevice has no quota). In this regard the Proxy Mobile IPv6 (PMIPv6 orPMIP) is returned to the HSGW server with the new PCO information. Inone example, special actions are included in the PCO. For example, themobile device is instructed not to ping the network unless a request toaccess the network is specifically initiated by the mobile device user.

In step 10, the HSGW sends a Point to Point Protocol, Vendor-SpecificNetwork Control Protocol Configuration Acknowledgment(PPP-VSNCP-Config-Ack) within the PCO information to the mobile device.

In step 11, the HSGW sends a PPP-VSNCP-Config Request to the mobiledevice (UE).

In step 12, the mobile device (UE) responds to the HSGW server with aPPP-VSNCP-Config-Ack. The mobile device parses the PCO information toretrieve subscriber status and follows instructions therein.

In step 13, the session continues as normal, providing communicationbetween the mobile device and the network.

As shown by the above discussion, functions relating to providingnetwork status information may be implemented on computers connected fordata communication via the components of a packet data network,operating as the OCS 208 and/or as a Customer Communication System 41 asshown in FIG. 1. Although special purpose devices may be used, suchdevices also may be implemented using one or more hardware platformsintended to represent a general class of data processing device commonlyused to run “server” programming so as to implement the network statusinformation functions discussed above, albeit with an appropriatenetwork connection for data communication.

FIGS. 9 and 10 provide functional block diagram illustrations of generalpurpose computer hardware platforms. FIG. 9 illustrates a network orhost computer platform, as may typically be used to implement a server.FIG. 10 depicts a device with user interface elements, as may be used toimplement a personal computer, such as computer 31 of FIG. 1, orworkstation or to implement a mobile device, such as a portable handset,a smart-phone, tablet computer, a personal digital assistant or othertype of mobile station or mobile terminal device (e.g., devices 13 a to13 f of FIGS. 1 and 2), although the device of FIG. 10 may also act as aserver if appropriately programmed. It is believed that the generalstructure and general operation of such equipment as shown in FIGS. 9and 10 should be self-explanatory from the high-level illustrations.

A general purpose computer configured as a server, for example, includesa data communication interface for packet data communication. The servercomputer also includes a central processing unit (CPU), in the form ofone or more processors, for executing program instructions. The serverplatform typically includes an internal communication bus, programstorage and data storage for various data files to be processed and/orcommunicated by the server, although the server often receivesprogramming and data via network communications. The hardware elements,operating systems and programming languages of such servers areconventional in nature. Of course, the server functions may beimplemented in a distributed fashion on a number of similar platforms,to distribute the processing load. In this case, such a platform wouldrun server programming, for example, to provide account statusinformation to the mobile device so as to function as one of the servers208, 39, 41, and 43 in FIG. 1.

A user terminal such as a general-purpose personal computer or a mobiledevice typically comprises a central processor or other processingdevice, an internal communication bus, various types of memory orstorage media (RAM, ROM, EEPROM, cache memory, disk or flash drives formass storage, etc.) for code and data storage, and one or more networkor communication interfaces or ports for communication purposes. Thesoftware functionalities involve programming, including executable codeas well as associated stored data, e.g. files used for applications onthe mobile device to process the instructions received from the network.The software code is executable by the mobile device. In operation, thecode is stored within the mobile device. At other times, however, thesoftware may be stored at other locations and/or transported for loadinginto the appropriate mobile device system. Execution of such code by aprocessor of the mobile device enables the mobile device to performfunctions of receiving network instructions on the account status, inessentially the manner performed in the implementations discussed andillustrated herein.

Hence, aspects of the methods of receiving and processing network statusinformation as outlined above may be embodied in programming. Programaspects of the technology may be thought of as “products” or “articlesof manufacture” typically in the form of executable code and/orassociated data that is carried on or embodied in a type ofnon-transitory machine readable medium.

While the foregoing has described what are considered to be the bestmode and/or other examples, it is understood that various modificationsmay be made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that the teachings may beapplied in numerous applications, only some of which have been describedherein. It is intended by the following claims to claim any and allapplications, modifications and variations that fall within the truescope of the present teachings.

Unless otherwise stated, all measurements, values, ratings, positions,magnitudes, sizes, and other specifications that are set forth in thisspecification, including in the claims that follow, are approximate, notexact. They are intended to have a reasonable range that is consistentwith the functions to which they relate and with what is customary inthe art to which they pertain.

The scope of protection is limited solely by the claims that now follow.That scope is intended and should be interpreted to be as broad as isconsistent with the ordinary meaning of the language that is used in theclaims when interpreted in light of this specification and theprosecution history that follows and to encompass all structural andfunctional equivalents. Notwithstanding, none of the claims are intendedto embrace subject matter that fails to satisfy the requirement ofSections 101, 102, or 103 of the Patent Act, nor should they beinterpreted in such a way. Any unintended embracement of such subjectmatter is hereby disclaimed.

Except as stated immediately above, nothing that has been stated orillustrated is intended or should be interpreted to cause a dedicationof any component, step, feature, object, benefit, advantage, orequivalent to the public, regardless of whether it is or is not recitedin the claims.

It will be understood that the terms and expressions used herein havethe ordinary meaning as is accorded to such terms and expressions withrespect to their corresponding respective areas of inquiry and studyexcept where specific meanings have otherwise been set forth herein.Relational terms such as first and second and the like may be usedsolely to distinguish one entity or action from another withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions. The terms “comprises,” “comprising,”or any other variation thereof, are intended to cover a non-exclusiveinclusion, such that a process, method, article, or apparatus thatcomprises a list of elements does not include only those elements butmay include other elements not expressly listed or inherent to suchprocess, method, article, or apparatus. An element proceeded by “a” or“an” does not, without further constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises the element.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter.

Appendix: Acronym List

The description above has used a large number of acronyms to refer tovarious services, notification messages, and system components. Althoughgenerally known, use of several of these acronyms is not strictlystandardized in the art. For the convenience of the reader, thefollowing list correlates terms to acronyms, as used by way of examplein the detailed description above.

3GPP2 —3'rd Generation Partnership Project 2

AAA—Authentication, Authorization, and Accounting

AAR—Authentication Authorization Request

AH—Account Holder

BS—Base Station

BTS—Base Transceiver System

CCA—Credit Control Answer

CCA-I—Credit Control Answer Initial

CCR—Credit Control Request

CCR-I—Credit Control Request Initial

CCRU—Credit Control Request Update

CPU—Central Processing Unit

EHRPD—Evolved High Rate Packet Data

EPC—Evolved Packet Core

EPS—Evolved Packet System

EPROM—Erasable Programmable Read Only Memory

EEPROM—Electrically Erasable Programmable Read Only Memory

eNB—Evolved Node B

E RAB—Evolved Packet System Radio Access Bearer

FLASH-EPROM—Flash Erasable Programmable Read Only Memory

FUI—Final Unit Indication

HRPD—High Rate Packet Data

HSGW—High Rate Packet Data Serving Gateway

HSS—Home Subscriber Server

ID—Identification

LTE—Long Term Evaluation

MD—Mobile Device

MME—Mobility Management Entity

MMSC—Multimedia Messaging Service Center

MSISDN—Mobile Station International Subscriber Directory Number

NAS—Non Access Stratum

OCS—Online Charging System

PCEF—Policy Control Enforcement Function

PCO—Protocol Configuration Option

PCRF—Policy and Charging Rules Function

PDN—Packet Data Network

PGW—Packet Data Network Gateway

PMIP—Proxy Mobile IPv6

PPP-VSNCP—Vendor-Specific Network Control Protocol Configuration

PROM—Programmable Read Only Memory

PSTN—Public Switched Telephone Network

QCI—Quality of Service Class Identifier

QoS—Quality of Service

RAM—Random Access Memory

RAN—Radio Access Network

RAR—Re-Authorization Request

ROM—Read Only Memory

RRC—Radio Resource Control

SAE—System Architecture Evolution

SGW—Serving Gateway

SIM—Subscriber Identity Module

SPR—Subscription Profile Repository

UL—Up Link

UDR—User Data Request

WAN—Wide Area Network

What is claimed is:
 1. A method, comprising steps of: tracking, on atleast one server, a data usage of a mobile device through a wirelesspacket data communication network; determining, from an account for themobile device stored on the at least one server, a data usage criterion;comparing, on the at least one server, the data usage to the data usagecriterion; and upon determining, based on the comparing, that the datausage has met the data usage criterion, sending a notification messageof the data usage having met the data usage criterion from the at leastone server to the mobile device in real time through a protocolconfiguration option (PCO) information element field within an existingmessage in a bearer channel of the wireless packet data communicationnetwork, the notification message comprising instructions to provide aplurality of options on a user interface of the mobile device by whichto update the account, the plurality of options including at least twoof changing a Quality of Service (QoS) associated with the account,changing the account to a different subscription plan from the provider,and suspending service on the account until a next billing cycle begins.2. The method of claim 1, wherein the notification message to the mobiledevice further comprises instructions to provide at least one option ona user interface of the mobile device to replenish the account.
 3. Themethod of claim 2, wherein the instructions to provide the at least oneoption on the user interface to replenish the account instruct themobile device to redirect the mobile device to a web site of an accountprovider where the at least one option is provided.
 4. The method ofclaim 1, wherein the notification message to the mobile device furthercomprises instructions to cause the mobile device to deactivate or blocktransmission of automatic network access requests originating from themobile device to the network.
 5. The method of claim 4, wherein theinstructions to cause the mobile device to deactivate or blocktransmission of automatic network access requests further configure themobile device to allow user-initiated network access requests.
 6. Themethod of claim 1, wherein the data usage criterion is one of at least(i) voice call minutes, (ii) data volume downloaded to the mobiledevice, or (iii) date and time the network is accessed.
 7. The method ofclaim 1, wherein the notification message is provided to all mobiledevices associated with the account.
 8. The method of claim 1, furthercomprising providing, upon determining that the mobile device isdifferent from a mobile device of an account holder, the notificationmessage to the mobile device of the account holder in addition to themobile device.
 9. The method of claim 1, wherein the plurality ofoptions on the user interface by which to update the account includes:changing a Quality of Service (QoS) associated with the account;changing the account to a different subscription plan from the provider;and suspending service on the account until a next billing cycle begins.10. The method of claim 1, wherein the notification message of the datausage having met the data usage criterion includes at least one of: anindication that money on the account has run out; an indication that adata limit on the account has been reached; and an indication that theaccount is under a data restriction.
 11. The system of claim 1, whereinthe plurality of options on the user interface by which to update theaccount includes: changing a Quality of Service (QoS) associated withthe account; changing the account to a different subscription plan fromthe provider; and suspending service on the account until a next billingcycle begins.
 12. A computer system configured as at least one server,the computer system comprising: a processor; a network interface coupledto the processor configured to enable communications via a communicationnetwork; a storage device for content and programming; a program storedin the storage device, wherein execution of the program by the processorconfigures the computer system to perform functions, including functionsto: track a data usage of a mobile device through a wireless packet datacommunication network; determine, from an account for the mobile devicestored on the storage device, a data usage criterion; compare the datausage to the data usage criterion; and upon determining, based on thecomparing, that the data usage has met the data usage criterion, send anotification message of the data usage having met the data usagecriterion from the at least one server to the mobile device in real timethrough a protocol configuration option (PCO) information element fieldwithin an existing message in a bearer channel of the wireless packetdata communication network, the notification message comprisinginstructions to provide a plurality of options on a user interface ofthe mobile device by which to update the account, the plurality ofoptions including at least two of changing a Quality of Service (QoS)associated with the account, changing the account to a differentsubscription plan from the provider, and suspending service on theaccount until a next billing cycle begins.
 13. The system of claim 12,wherein the notification message to the mobile device further comprisesinstructions to provide at least one option on a user interface of themobile device to replenish the account.
 14. The system of claim 13,wherein the instructions to provide the at least one option on the userinterface to replenish the account instruct the mobile device toredirect the mobile device to a web site of an account provider where atleast one option is provided.
 15. The system of claim 12, wherein thenotification message to the mobile device further comprises instructionsto cause the mobile device to deactivate or block transmission ofautomatic network access requests originating from the mobile device tothe network.
 16. The system of claim 15, wherein the instructions tocause the mobile device to deactivate or block transmission of automaticnetwork access requests further configure the mobile device to allowuser-initiated network access requests.
 17. The system of claim 12,wherein the data usage criterion is one of at least (i) voice callminutes, (ii) data volume downloaded to the mobile device, or (iii) dateand time the network can be accessed.
 18. The system of claim 12,wherein the notification message is provided to all mobile devicesassociated with the account.
 19. The system of claim 12, wherein thefunctions further include a function to provide, upon determining thatthe mobile device is different from a mobile device of an accountholder, the notification message to the mobile device of the accountholder in addition to the mobile device.
 20. The system of claim 12,wherein the notification message of the data usage having met the datausage criterion includes at least one of: an indication that money onthe account has run out; an indication that a data limit on the accounthas been reached; and an indication that the account is under a datarestriction.